docs: document deleting custom identity schemas#2539
Conversation
KT-Doan
changed the title
Co-authored-by: unatasha8 <una.cogavin@ory.sh>
|
What do you mean by "an attachment to a project is permanent for the lifetime of that project"? You are able to change a project's schema so a schema is not permanently 'attached' for the lifetime of the project. |
When we add a schema to a project its attached to the historical project revision, so identities can still reference that schema even if it's technically not in the project's current state |
So once a schema has been added to a project it cannot be deleted. |
That is correct, at least not for now. This is the current state as we haven't found a good way of deleting schemas that are attached to a project w/out breaking things. |
KT-Doan
changed the title
|
This feature has been released @unatasha8 PTAL again! |
Drop "currently" from the Console disabled-button note (an attachment is permanent for the project's lifetime, so it is never merely current) and replace "still in use" with the explicit "used by a project or referenced by an identity" condition.
|
I'm not sure what else is required for the failing tests @unatasha8 , please assist when you can! |
4 participants
Summary
Adds a "Delete a custom schema" section to the manage identity schemas page, covering both the Console UI flow and a cURL example using a workspace API key against the Console API.
Documents the constraints surfaced by the API: the deletion is rejected (409) if the schema is still attached to a project or referenced by an identity. The section also calls out that presets cannot be deleted and that an attachment to a project is permanent for the lifetime of that project.
Pairs with the cloud-side endpoint and Console UI changes that introduced the delete capability.
Test plan
personal-access-token.mdx#authorizing-ory-network-workspace-admin-apisresolve<ConsoleLink route="project.identitySchema" />resolves to the existing schema page